Improve Markover review UI - #195
Draft
lastobelus wants to merge 3 commits into
Draft
Conversation
This was referenced Aug 21, 2026
Owner
Author
Work intentphase: review
summary: "PR #195 human-QA refinements are implemented, validated, pushed, and live in the development watcher for visual review."
touch-points:
- src/index.html
- src/renderer.ts
- src/styles.css
- test/accessibility.test.ts
- test/brand.test.ts
- test/review-inbox-ui.test.ts
done-when:
- "The app header is approximately 80% of its prior height while the logo retains its current size and controls remain usable."
- "The checksum is absent by default and available only through an explicit development-build option."
- "Source changed remains in the header and is repeated in the Source card when applicable."
- "The left- and right-pane navigation tabs share the right-pane underline visual grammar."
- "The redundant Needs me / shown list heading is removed without losing an accessible list name."
- "The pr-195 watcher rebuilds to ready and focused plus full local validation pass."
excludes:
- "Moving Source changed out of the header."
- "Changing the center-pane All/Annotated segmented filter."
- "Shrinking the Markover logo."
- "Naming or redesigning unrelated components."
- "Merging PR #195."
blocked-by: []
may-block: []
branch: "t3code/improve-markover-ui" |
This was referenced Aug 21, 2026
lastobelus
force-pushed
the
t3code/improve-markover-ui
branch
2 times, most recently
from
August 21, 2026 23:35
110c17a to
7769796
Compare
Squash the Claude-driven incremental UI series into one net change so it can be rebased cleanly onto the canonical app structure vocabulary.
lastobelus
force-pushed
the
t3code/improve-markover-ui
branch
from
August 25, 2026 21:12
d5e1e7e to
edb657c
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Claude’s incremental UI experiment is rebuilt on the canonical app-structure vocabulary landed in #199 and rebased onto
main.The inherited UI changes include:
The latest human-QA pass also:
Naming and theme-token foundation
#199 owns the canonical names: App shell, App header, Pane layout, Left pane, Center pane, and Right pane. This PR uses those names throughout its DOM, TypeScript, CSS, settings, tests, and structural semantic tokens.
The floating development palette is consistently named the theme-token inspector so it does not collide with Markover’s Ember/Ocean/Olive palette setting. It:
--theme-token-inspector-*component roles--app-header-backgroundThe architecture documentation records this PR’s current structural color mappings.
Validation
npm run ci:localStatus
Draft while human UI QA continues. The PR #195 development watcher is live and ready on the current head.
🤖 Original incremental UI work generated with Claude Code; branch split, rebase, naming alignment, token audit, and subsequent human-QA refinements completed with Codex.